[Storage] [STG 103/104] Changelog updates + date for release#48006
[Storage] [STG 103/104] Changelog updates + date for release#48006weirongw23-msft wants to merge 1 commit into
Conversation
| `BlobClient` upload operations (`stage_block`, `stage_block_from_url`, `upload_page`, | ||
| `upload_pages_from_url`, `append_block`, `append_block_from_url`, `upload_blob`, and | ||
| `upload_blob_from_url`) in addition to `content_md5` when a content MD5 is | ||
| provided with the request. |
There was a problem hiding this comment.
Add an "Other Changes" section about the block IDs. Something like "Partitioned upload via upload_blob with Block Blobs will now generate random, unique block ids for each block rather than using a sequential count. The length of the new block ids will be the same as previous versions to ensure backwards compatibility."
| ## 12.26.0b1 (Unreleased) | ||
| ## 12.26.0b1 (2026-07-21) | ||
|
|
||
| ### Features Added |
There was a problem hiding this comment.
What about - Added support for service version 2026-10-06. That would give you something to put here.
| ## 12.18.0b1 (Unreleased) | ||
| ## 12.18.0b1 (2026-07-21) | ||
|
|
||
| ### Features Added |
There was a problem hiding this comment.
- Added support for service version 2026-10-06.
| service responses. | ||
| - Added a new `FileRange` model with `start`, `end`, and `cleared` properties. | ||
|
|
||
| ### Other Changes |
There was a problem hiding this comment.
Let's put an entry here and in Queue for the TypeSpec migration. "Migrated generated code to use new TypeSpec generator." - This won't mean much to customers but is good to know for internal use.
Updated the release date (for now) to 2026-07-21.
Two questions:
_sharedfolder changes from the Unique Put Block IDs feature. Is it fine to leave blank? We've had releases whereFeatures Addedwere left blank.Features Added,Bugs Fixedare both weird. We could potentially consider specifying this inOther Changes, but again none that directly affect the users because they're generated code.